home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group94a.txt
/
000155_icon-group-sender _Thu Jun 2 14:15:20 1994.msg
< prev
next >
Wrap
Internet Message Format
|
1994-08-19
|
2KB
Received: by cheltenham.cs.arizona.edu; Thu, 2 Jun 1994 15:48:57 MST
Date: Thu, 2 Jun 94 14:15:20 PDT
From: eric@star-semi.com (Eric Armstrong)
Message-Id: <9406022115.AA26472@star-semi.com>
To: icon-group@cs.arizona.edu
Subject: email system??
Status: R
Errors-To: icon-group-errors@cs.arizona.edu
QUESTION 1 (of 2)
-----------------
Have a wild idea in mind:
. Find sources for a basic email system
--preferably one that includes some kind of command processor,
like ftp mail
. Customize it using Icon
. Modify it to track bug status, log software changes, and describe
new features.
Our situation, basically is:
. we're a small company in a growth spurt
. we need to start tracking things like these in a methodical way
. we can't afford a lot of overhead (huge database system with 10
administrators)
. we are distributed, with people working on both coasts (so a
central database-oriented approach is not feasible
The basic idea is to send an email to a cataloging system that understands
some simple commands, can attach messages to different topical "threads", and
allow retreiving as-yet-unread messages -- basically a NEWS kind of application,
now that I think of it.
QUESTION 2 (of 2)
-----------------
Since any existing program that fills the bill is likely to have been written
in C, and since Icon is so very good at sensible string manipulation and
pattern matching, can anyone give me tips on C-to-Icon translation? (I figure
to do the "smart stuff" at the highest levels in Icon, and call all the low
level nitty-gritty stuff in C.
Can anyone point me to something that will get me started down the right path?
Thanks!